From 97ae3c020268b1208f6efa83e2eb156ba6ad2648 Mon Sep 17 00:00:00 2001 From: Keir Fraser Date: Tue, 18 Mar 2008 11:06:26 +0000 Subject: [PATCH] Set device model when creating rfb console via XenAPI When creating a rfb console via XenAPI the device model is not being set to qemu-dm, resulting in no pvfb since qemu-dm is not launched when domU is started. This patch sets device model when a rfb console is created via XenAPI. Signed-off-by: Jim Fehlig --- tools/python/xen/xend/XendConfig.py | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/tools/python/xen/xend/XendConfig.py b/tools/python/xen/xend/XendConfig.py index ec9c8c5c31..f703808da1 100644 --- a/tools/python/xen/xend/XendConfig.py +++ b/tools/python/xen/xend/XendConfig.py @@ -1282,6 +1282,12 @@ class XendConfig(dict): target['devices'][dev_uuid] = ('vfb', dev_info) target['console_refs'].append(dev_uuid) + # if console is rfb, set device_model ensuring qemu + # is invoked for pvfb services + if 'device_model' not in target['platform']: + target['platform']['device_model'] = \ + xen.util.auxbin.pathTo("qemu-dm") + # Finally, if we are a pvfb, we need to make a vkbd # as well that is not really exposed to Xen API vkbd_uuid = uuid.createString() -- 2.30.2